Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid many-to-many join by collapsing records by claim using max-by #124

Conversation

pschichtel
Copy link
Contributor

This should fix #105

@abhilashshetty04
Copy link
Member

@pschichtel , Are these non Mayastor volumes? As we do not support ReadWriteMany.

Copy link
Member

@abhilashshetty04 abhilashshetty04 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm, Thanks :)

@pschichtel
Copy link
Contributor Author

@abhilashshetty04 No, ReadWriteOnce (but not ReadWriteOncePod), so the volume can still be mounted by multiple pods, the post will be scheduled onto the same node though.

@abhilashshetty04 abhilashshetty04 merged commit d2dc720 into openebs:develop Jan 31, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

StalePersistentVolumeClaim duplicate time series in Victoria Metrics
2 participants